Intelligent vehicle navigator

ABSTRACT

Methods, systems, and storage media relating to a vehicle navigator system are disclosed herein. In an embodiment, vehicle operation data relating to one or more characteristics of operation of a motor vehicle may be received. An operation style by which an operator may operate the motor vehicle may be determined from the vehicle operation data. A vehicle location and a destination location may be received. A route may be determined from the vehicle location to the destination location according to the operation style by which an operator operates the motor vehicle. Other embodiments may be disclosed and/or claimed.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/664,394, filed Oct. 25, 2019, which is a continuation of U.S.application Ser. No. 15/499,802, filed Apr. 27, 2017, now issued as U.S.Pat. No. 10,488,213, all of which are incorporated herein by referencein their entirety.

FIELD

The present disclosure relates to the field of on-board vehiclenavigator systems, and in particular, to apparatuses, methods andstorage media associated with such systems.

BACKGROUND

Some on-board vehicle navigator systems may receive vehicle locationinformation from a location system, which may communicate with asatellite positioning system such as the Global Positioning System (GPS)or an analogous system, to indicate a location of the vehicle to anoperator or another occupant of the vehicle. Such navigator systems mayreceive or obtain a destination location and may cooperate with a map ormapping system to provide for the operator and/or an occupant a routefrom the vehicle location to the destination location. In someimplementations, the route may be provided based a default and/or anoperator-selected criterion such as “fastest route.”

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings.

FIG. 1 is a block diagram of a vehicle navigator system, according tosome embodiments.

FIG. 2 is a flow flowchart illustrating an example process of providinga route to a destination according to a route type that may correspondto an operator's vehicle operation style.

FIG. 3 is a block diagram illustrating components of the vehiclenavigator system of FIG. 1 , according to some embodiments.

FIG. 4 schematically illustrates an example computing device inaccordance with one embodiment.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustrated embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed to imply that the various operations are necessarilyorder-dependent. In particular, these operations might not be performedin the order of presentation. Operations described may be performed in adifferent order than the described embodiments. Various additionaloperations might be performed, or described operations might be omittedin additional embodiments.

The description may use the phrases “in an embodiment”, “in animplementation”, or in “embodiments” or “implementations”, which mayeach refer to one or more of the same or different embodiments.Furthermore, the terms “comprising.” “including,” “having,” and thelike, as used with respect to embodiments of the present disclosure, aresynonymous.

As used herein, the term “logic” and “module” may refer to, be part of,or include any or any combination of an Application Specific IntegratedCircuit (ASIC), an electronic circuit, a programmable combinatorialcircuit (such as field programmable gate arrays (FPGA))m a processor(shared, dedicated, or group) or memory (shared, dedicated, or group)that execute one or more software or firmware programs, or othersuitable components that provide the described functionality.

Also, it is noted that example embodiments may be described as a processdepicted with a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart may describethe operations as a sequential process, many of the operations may beperformed in parallel, concurrently, or simultaneously. In addition, theorder of the operations may be re-arranged. A process may be terminatedwhen its operations are completed, but may also have additional stepsnot included in a figure. A process may correspond to a method, afunction, a procedure, a subroutine, a subprogram, and the like. When aprocess corresponds to a function, its termination may correspond to areturn of the function to the calling function a main function.

As disclosed herein, the term “memory” may represent one or morehardware devices for storing data, including random access memory (RAM),magnetic RAM, core memory, read only memory (ROM), magnetic disk storagemediums, optical storage mediums, flash memory devices or other machinereadable mediums for storing data. The term “computer-readable medium”may include, but is not limited to, memory, portable or fixed storagedevices, optical storage devices, and various other mediums capable ofstoring, containing or carrying instructions or data.

Furthermore, example embodiments may be implemented by hardware,software, firmware, middleware, microcode, hardware descriptionlanguages, or any combination thereof. When implemented in software,firmware, middleware or microcode, the program code or code segments toperform the necessary tasks may be stored in a machine or computerreadable medium. A code segment may represent a procedure, a function, asubprogram, a program, a routine, a subroutine, a module, program code,a software package, a class, or any combination of instructions, datastructures, program statements, and the like.

As used herein, the term “network element”, may be considered synonymousto or referred to as a networked computer, networking hardware, networkequipment, router, switch, hub, bridge, gateway, or other like device.The term “network element” may describe a physical computing device of anetwork with wired or wireless communication links. Furthermore, theterm “network element” may describe equipment that provides radiobaseband functions for data or voice connectivity between a network andone or more users.

FIG. 1 is a block diagram of a vehicle navigator system 100, accordingto some embodiments. Vehicle navigator system 100 may be disposed in oron-board a vehicle 105. In some embodiments, vehicle 105 may include amotor vehicle such as an automobile or a truck, for example.

Vehicle navigator system 100 may include a controller 110 and one ormore connections 115 a-115 c, for example, which may be disposed invehicle 105 between controller 110 and one or more data sources 120a-120 c, respectively. In embodiments, data sources 120 a-120 c mayinclude a vehicle data port 120 a that may be connected to andcommunicate with controller 110 via connection 115 a. A vehiclediagnostic system 120 a-1 may communicate with controller 110 viavehicle data port 120 a regarding one or more on-board vehiclediagnostic or operating characteristics such as speed, engine RPM,emission characteristics, etc. In embodiments, one or more vehiclesensors 120 a-2 may determine, sense, and/or provide to controller 110data regarding one or more other vehicle characteristics, which data maynot be provided by vehicle diagnostic system 120 a-1. In someembodiments, the one or more other vehicle characteristics may includeany or all of seat belt connection status, horn operation, extent and/orfrequency of shock absorber operation, ignition status, hard braking,etc. In embodiments, data from vehicle diagnostic system 120 a-1 and/orvehicle sensors 120 a-2 may be referred to as vehicle operation data.

Vehicle navigator system 100 may include connection 115 b betweencontroller 110 and a location system 120 b, which may be located onand/or associated with vehicle 105 to provide to controller 110 vehiclelocation information that may indicate a location of vehicle 105. Inembodiments, location system 120 b may communicate and operate inassociation with a positioning system, such as a satellite positioningsystem like GPS, or an analogous positioning system. Vehicle navigatorsystem 100 may also include a connection 115 c between controller 110and a map or mapping system 120 c. In some embodiments, map or mappingsystem 120 c may be included in or integral with vehicle navigatorsystem 100 and located on-board vehicle 105 and/or may be accessed overa wireless network from a mapping service provider.

Vehicle navigator system 100 may also include a connection 115 d betweencontroller 110 and a mobile communication device 130, which may providewireless communication between vehicle navigator system 100 and one ormore remote network-connected systems and/or services. In someembodiments, for example, mobile communication device 130 may beintegral with vehicle navigator system 100 and/or may include a separatemobile telephone local to and in communication with vehicle navigatorsystem 100. For example, communication between vehicle navigator system100 and a remote mapping system 120 c may be carried via connection 115d and mobile communication device 130. In some embodiments, such as whenit is a separate mobile telephone in communication with vehiclenavigator system 100, mobile communication device 130 may provide and/oroperate as a user interface for vehicle navigator system 100. In otherembodiments, vehicle navigator system 100 may include a dedicated userinterface.

Controller 110 may determine from the vehicle operation data at leastone of a plurality of operation styles by which an operator may operatethe vehicle. In embodiments, the plurality of operation styles maycorrespond to or correlate with one or more of a fuel-efficientoperation style, a safe operation style, and/or a fastest routeoperation style, for example. In embodiments, other operation styles maybe included, such as a scenic route operation style, for example. As anexample, Table 1 lists vehicle operation data that may be associatedand/or correlated with fuel-efficient and safest operation styles, forexample.

TABLE 1 Vehicle Road Attributes from Operation Style Route Type Sensordata Diagnostic Data map data Safest Safest Seat belt Speed Express way(Freeway) Honk Carriage way (undivided Shock absorber highway) Dividedway (divided highway) Speed limits Fuel Efficient Fuel EfficientIgnition Speed Traffic density and Shock absorber RPM variation EmissionSurface texture Smoothness Pavement stiffness

In some embodiments, vehicle operation data may be correlated withroutes used by a vehicle operator to determine one or more operationstyles used by the vehicle operator. In other embodiments, determinationof one or more vehicle operation styles may be further correlated withvehicle operation times, which may include days of the week and/or timesof day. In some embodiments, the operation style may be furthercorrelated with time of day, day of week, and/or a frequency orregularity at which the operator goes to the destination and may furtherinclude in the operation style a transportation style such commuting,errands, recreation, etc.

Vehicle navigator system 100 may receive vehicle location informationfrom location system 120 b, and the location information may becorrelated with a map from mapping system 120 c to indicate a locationof the vehicle 105. Further, vehicle navigator system 100 may receive adestination location to which the operator may plan or intend to operatevehicle 105. In embodiments, the destination location may be selected orentered by the operator, or another person, or may be received by orretrieved from vehicle navigator system 100, by operation of one or moreof location system 120 b, mapping system 120 c, mobile communicationdevice 130, and/or a user interface that may be included or associatedwith vehicle navigator system 100. Mapping system 120 c may furtherprovide road attribute information which may include any or all ofplural road types, such as Express way (Freeway). Divided way (dividedhighway). Carriage way (undivided highway), and speed limits

In embodiments, controller 110 may provide a route from the vehiclelocation to the destination location according to a route type that maycorrespond to or be associated with at least one of the plurality ofoperation styles by which the operator may operate the vehicle. Forexample, Table 1 lists route types that may correspond to operationstyles. In some embodiments, controller 110 may provide the route typebased on determination of at least one of the plurality of operationstyles by which the operator may operate the vehicle and without anexplicit input by the operator to the navigator system 100 of anoperation style or a route type.

In an embodiment, vehicle operation data that may correspond with asafest operation style and may suggest an operator preference for asafest route may include, for example, any or all of proper and/orregular use of seat belts, infrequent or no honking, no or infrequentsudden braking, and/or staying within speed limits according to vehiclediagnostic and mapping system information. As an example, a safest routetype that may correspond to a safest operation style of an operator mayinclude road attributes that may include any or all of: express ways,motor ways, divided roads, appropriate speed limits and breaks, whichinformation may be available from mapping system 120 c, for example.Some embodiments may include other safety related information as well.

In an embodiment, vehicle operation data that may correspond with a fuelefficient operation style and may suggest an operator preference for afuel efficient route may include, for example, any or all of constantspeed and RPM levels, low or moderate emission levels, and/or shockabsorbers in good state. As an example, a fuel efficient route type thatmay correspond to a fuel efficient operation style of an operator mayinclude road attributes such as constant or steady traffic density andvariation and road smoothness, which data may be available from mappingsystem 120 c, for example.

Before further describing vehicle navigator system 100, it should benoted that while for ease of understanding, vehicle navigator system 100was illustrated having data sources 120 a-120 c, and connections 115a-115 d, in alternate embodiments, there might be more or less datasources, e.g., location system 120 b and mapping system 120 c may becombined, or mapping system 120 c may be splitted into multiple systems,such as route system, point-of-interest system, and so forth; and theremight be more or less connections 115 a-115 d, e.g., some connectionsmay be combined and shared, or other connections such as a parallelconnection to 115 a may be added. The elements and their connections aremerely illustrated, and not to be read as limiting.

FIG. 2 is a flow flowchart illustrating an example process 200 ofproviding a route to a destination according to a route type that maycorrespond to an operator's vehicle operation style. For illustrativepurposes, the operations of process 200 will be described as beingperformed by vehicle navigator system 100 (FIG. 1 ). However, it shouldbe noted that other computing devices may operate the process 200, whichother devices may include networked or other computing devices that maybe remote from vehicle 105 and may be in communication with a mobilecommunication device on-board the vehicle 105. While particular examplesand orders of operations are illustrated in FIG. 2 , in variousembodiments, these operations may be re-ordered, separated intoadditional operations, combined, or omitted altogether.

At operation 205, vehicle operation data relating to one or morecharacteristics of operation of a motor vehicle may be received. In someembodiments, the vehicle operation data may be provided by a vehiclediagnostic system 120 a-1 and/or one or more vehicle sensors 120 a-2.

At operation 210, an operation style by which an operator may operatethe motor vehicle may be determined from the vehicle operation data. Inembodiments, the operation style may be determined as at least one of aplurality of operation styles. For example, in some embodiments, theoperation style may be determined by a computing device that may beremote from vehicle 105.

At operation 215, a vehicle location may be received.

At operation 220, a destination location may be received.

At operation 225, a route may be determined from the vehicle location tothe destination location according to the operation style by which anoperator operates the motor vehicle. In embodiments, the route may bedetermined from mapping data as one of a plurality of route types thatmay correspond to the operation style of the operator. In embodiments, anumber of candidate routes may first be identified between the vehiclelocation and the destination location. Then, a route type (such as saferoute, fastest route, and so forth) may be determined for the variouscandidate routes, based at least in part on route data (e.g., frommapping system 120 c). Next, the suitable route may be selected based onthe compatibility of the route types of the candidate routes with theoperation style of the driver of vehicle 105.

At operation 230, the route determined according to the operation styleby which an operator operates the motor vehicle may be provided to thevehicle operator. In embodiments, providing the route to the vehicleoperator may include displaying or announcing the route and/ordirections for the route on a user interface device. In someembodiments, the user interface device may include a mobile wirelessdevice such as a mobile telephone.

In embodiments, multiple drivers may be supported. In other words,operation styles may be determined for different drivers of the vehicle,e.g., a primary driver, and a secondary driver, and the selection ofroute may be based further on the operation style of the current driver.In embodiments, the identity of the driver may be provided to vehiclenavigation system 100 by the driver. In other embodiments, vehiclenavigator system 100 may be provided with additional components and/orlogic to recognize the driver, e.g., through bio-metrics, such asfingerprints, iris, facial recognition, and so forth. In otherembodiments, vehicle navigator system 100 may recognized the driver bythe current operating style.

In embodiments, a driver may be computer assisted or a driver may be anautonomous driving system. Thus, a driver may be referred to as anoperator, which may be human, machine, or combination thereof.

FIG. 3 is a block diagram illustrating components of vehicle navigatorsystem 100, according to some embodiments. Controller 110 may includeany or any combination of an Application Specific Integrated Circuit(ASIC), an electronic circuit, a programmable combinatorial circuit(e.g., FPGA), a processor (shared, dedicated, or group) or memory(shared, dedicated, or group) that may execute one or more software orfirmware programs, or other suitable components that provide thedescribed functionality. In some embodiments, controller 100 may employa software development kit (SDK) that may include and/or provide any orall of classifications 305 that may classify operation styles and/orroute types, one or more associations 310 between route types andoperation styles from which associations route may be provided, and/orAPIs 315 (e.g., public APIs) that may be used to develop applicationsfor automobile navigation systems, phones/connected devices, etc.

In embodiments, one or more of vehicle sensors 120 a-2 to determine,sense, and/or provide to controller 110 data regarding one or more othervehicle characteristics may be and/or include Internet of Things (“IoT”)devices. IoT devices may be objects or “things”, each of which may beembedded with hardware or software that may enable connectivity to anetwork, typically to provide information to a system, such ascontroller 110. Because the IoT devices are enabled to communicate overa network, the IoT devices may exchange event-based data with serviceproviders or systems in order to enhance or complement the services thatmay be provided. These IoT devices are typically able to transmit dataautonomously or with little to no user intervention. In embodiments,connection 115 a may accommodate vehicle sensors 120 a-2 as IoT devicesand may include IoT-compatible connectivity, which may include any orall of WiFi, BlueTooth, low-energy BlueTooth, USB, etc.

Embodiments of the present disclosure may be implemented into a systemusing any suitable hardware and/or software to configure as desired.FIG. 4 schematically illustrates a computing device 400 in accordancewith one embodiment. The computing device 400 may house a board such asmotherboard 402 (i.e. housing 451). The motherboard 402 may include anumber of components, including but not limited to a processor 404 andat least one communication chip 406. The processor 404 may include oneor more processor cores physically and electrically coupled to themotherboard 402. In some implementations, the at least one communicationchip 406 may also be physically and electrically coupled to themotherboard 402. In further implementations, the communication chip 406may be part of the processor 404. In embodiments, processor 404 mayinclude hardware accelerator 405 (e.g., FPGA).

Depending on its applications, computing device 400 may include othercomponents that may or may not be physically and electrically coupled tothe motherboard 402. These other components may include, but are notlimited to, volatile memory (e.g., DRAM) 420, non-volatile memory (e.g.,ROM) 424, and flash memory 422. In embodiments, flash 422 and/or ROM 424may include executable programming instructions 423 configured toimplement earlier described vehicle navigation system 100. Inembodiments, some aspects of navigation system 100, e.g., thedetermination of operation styles, or the matching of operation stylewith route type, may be implemented with hardware accelerator 405instead.

In embodiments, computing device 400 may further include a graphicsprocessor 430, a digital signal processor (not shown), a cryptoprocessor (not shown), a chipset 426, an antenna 428, a display (notshown), a touchscreen display 432, a touchscreen controller 446, abattery 436, an audio codec (not shown), a video codec (not shown), apower amplifier 441, a global positioning system (GPS) device 440, acompass 442, an accelerometer (not shown), a gyroscope (not shown), aspeaker 450, a camera 452, and a mass storage device (such as hard diskdrive, compact disk (CD), digital versatile disk (DVD), and so forth)(not shown). Further components, not shown in FIG. 4 , may include amicrophone, a filter, an oscillator, a pressure sensor, or an RFID chip.

The communication chip 406 may enable wireless communications for thetransfer of data to and from the computing device 400. The term“wireless” and its derivatives may be used to describe circuits,devices, systems, processes, techniques, communications channels, etc.,that may communicate data through the use of modulated electromagneticradiation through a non-solid medium. The term does not imply that theassociated devices do not contain any wires, although in someembodiments they might not. The communication chip 406 may implement anyof a number of wireless standards or protocols, including but notlimited to Institute for Electrical and Electronic Engineers (IEEE)standards including Wi-Fi (IEEE 802.11 family), IEEE 802.16 standards(e.g., IEEE 802.16-2005 Amendment), Long-Term Evolution (LTE) projectalong with any amendments, updates, and/or revisions (e.g., advanced LTEproject, ultra mobile broadband (UMB) project (also referred to as“3GPP2”), etc.). IEEE 802.16 compatible BWA networks are generallyreferred to as WiMAX networks, an acronym that stands for WorldwideInteroperability for Microwave Access, which is a certification mark forproducts that pass conformity and interoperability tests for the IEEE802.16 standards. The communication chip 406 may operate in accordancewith a Global System for Mobile Communication (GSM), General PacketRadio Service (GPRS), Universal Mobile Telecommunications System (UMTS),High Speed Packet Access (HSPA), Evolved HSPA (E-HSPA), or LTE network.The communication chip 406 may operate in accordance with Enhanced Datafor GSM Evolution (EDGE). GSM EDGE Radio Access Network (GERAN),Universal Terrestrial Radio Access Network (UTRAN), or Evolved UTRAN(E-UTRAN). The communication chip 406 may operate in accordance withCode Division Multiple Access (CDMA), Time Division Multiple Access(TDMA), Digital Enhanced Cordless Telecommunications (DECT).Evolution-Data Optimized (EV-DO), derivatives thereof, as well as anyother wireless protocols that are designated as 3G, 4G, 5G, and beyond.The communication chip 406 may operate in accordance with other wirelessprotocols in other embodiments.

The computing device 400 may include a plurality of communication chips406. For instance, a first communication chip 406 may be dedicated toshorter range wireless communications such as Wi-Fi and Bluetooth and asecond communication chip 406 may be dedicated to longer range wirelesscommunications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, Ev-DO, andothers.

The processor 404 of the computing device 400 may include a die in apackage assembly. The term “processor” may refer to any device orportion of a device that processes electronic data from registers and/ormemory to transform that electronic data into other electronic data thatmay be stored in registers and/or memory.

Some non-limiting Examples are provided below.

Example 1 may include an on-board vehicle navigator system, which mayinclude one or more vehicle sensors disposed in a vehicle to sense oneor more characteristics of operation of an operator of the vehicle; acontroller disposed in the vehicle and coupled with the one or morevehicle sensors; and a location system coupled with the controller,wherein the controller is to: receive data from the one or more sensorsas to the one or more characteristics of operation of an operator of thevehicle; receive vehicle location information from the location systemto indicate a location of the vehicle; obtain a destination location;and provide a route from the vehicle location to the destinationlocation for the operator, according to at least one of a plurality ofoperation styles by which the operator operates the vehicle, wherein theat least one of the plurality of operation styles by which the operatoroperates the vehicle is determined based at least in part on the datareceived from the one or more sensors.

Example 2 may include the system of example 1, wherein the controllermay determine the at least one of the plurality of operation stylesbased at least in part on the data received from the one or more sensors

Example 3 may include the system of example 1 or 2, wherein thecontroller may determine the at least one of the plurality of operationstyles without an explicit input by the operator to the system of the atleast one of the plurality of operation styles.

Example 4 may include the system of example 1 or 2, wherein thecontroller may further associate the plurality of operation styles witha plurality of route types.

Example 5 may include the system of example 4, wherein the plurality ofroute types may include one or more of a fuel-efficient route and a saferoute.

Example 6 may include the system of example 1 or 2 and may furtherinclude a communication connection to communicate with a mobilecommunication device.

Example 7 may include the system of example 6 wherein the controller mayfurther provide over the communication connection the at least one ofthe plurality of operation styles by which an operator operates thevehicle to be transmitted by the mobile communication device to bestored remotely.

Example 8 may include the system of example 6 wherein the controller mayfurther provide over the communication connection the route from thevehicle location to the destination location according to the at leastone of the plurality of operation styles by which the operator operatesthe vehicle to be transmitted by the mobile communication device to bestored remotely.

Example 9 may include the system of example 1 or 2 wherein the vehiclemay include a motor vehicle.

Example 10 may include the system of example 1 or 2 wherein one or moreof the vehicle sensors may include Internet-of-Things (IoT) sensors.

Example 11 may include an on-board vehicle navigator system, which mayinclude one or more vehicle sensors disposed in a vehicle to sense oneor more characteristics of operation of an operator of the vehicle; acontroller disposed in the vehicle, and coupled with the one or morevehicle sensors; and a location system coupled with the controller,wherein the controller is to: receive data from the one or more sensorsas to one or more characteristics of operation of an operator of thevehicle; receive vehicle location information from the location systemto indicate a location of the vehicle; obtain a destination location;determine from the data a route according to at least one of a pluralityof route types between the vehicle location and the destinationlocation; and provide a route for the operator from the vehicle locationto the destination location according to the at least one of theplurality of route types; wherein the route according to at least one ofthe plurality of route types between the vehicle location and thedestination location is determined based at least in part on the datareceived from the one or more sensors.

Example 12 may include the system of example 11, wherein the controllermay determine the route without an explicit input by the operator to thesystem of the at least one of the plurality of route types.

Example 13 may include the system of example 12, wherein the pluralityof route types may include one or more of a fuel-efficient route and asafe route.

Example 14 may include the system of example any of examples 11-13wherein the system may further include a communication connection tocommunicate with a mobile communication device.

Example 15 may include the system of example 14 wherein the controllermay further provide over the communication connection the routeaccording to at least one of the plurality of route types to betransmitted by the mobile communication system to be stored remotely.

Example 16 may include the system of example 14 wherein the controllermay further determine from the data at least one of a plurality ofoperation styles by which an operator operates the vehicle.

Example 17 may include the system of example 16 wherein the controllermay further provide over the connection at least one of a plurality ofoperation styles by which an operator operates the vehicle to betransmitted by the mobile communication device to be stored remotely.

Example 18 may include the system of example of any of examples 11-13,wherein one or more of the vehicle sensors may includeInternet-of-Things (IoT) sensors.

Example 19 may include at least one computer-readable storage mediumhaving a plurality of instructions, in response to execution by aprocessor of an on-board vehicle navigator system, may cause theon-board vehicle navigator system to: receive data from one or moresensors as to one or more characteristics of operation of an operator ofa motor vehicle; receive motor vehicle location information from alocation system to indicate a location of the motor vehicle; obtain aninput of a destination location; and provide a route for the operatorfrom the motor vehicle location to the destination location according tothe at least one of the plurality of operation styles by which theoperator operates the motor vehicle, wherein the at least one of theplurality of operation styles by which the operator operates the vehicleis determined based at least in part on the data received from the oneor more sensors.

Example 20 may include the at least one computer-readable storage mediumof example 19, wherein the at least one computer-readable storage mediummay further include instructions to determine the at least one of theplurality of operation styles based at least in part on the datareceived from the one or more sensors.

Example 21 may include the at least one computer-readable storage mediumof example claim 19 or 20, wherein the instructions to determine fromthe data at least one of a plurality of operation styles by which anoperator operates the motor vehicle may include instructions todetermine the at least one of the plurality of operation styles withoutan explicit input by the operator to the system of the at least one ofthe plurality of operation styles.

Example 22 may include the at least one computer-readable storage mediumof example 19 or 20, wherein the at least one computer-readable storagemedium may further include instructions to associate the plurality ofoperation styles with a plurality of route types.

Example 23 may include the at least one computer-readable storage mediumof example 22, wherein the plurality of route types may include one ormore of a fuel-efficient route and a safe route.

Example 24 may include the at least one computer-readable storage mediumof example 19 or 20 wherein the on-board vehicle navigator system mayinclude a communication connection to communicate with a mobilecommunication device.

Example 25 may include the at least one computer-readable storage mediumof example 24 wherein the at least one computer-readable storage mediummay further include instructions to provide over the communicationconnection the at least one of the plurality of operation styles bywhich an operator operates the motor vehicle to be transmitted by themobile communication device to be stored remotely.

Example 26 may include the at least one computer-readable storage mediumof example 24 wherein the at least one computer-readable storage mediummay further include instructions to provide over the communicationconnection the route from the motor vehicle location to the destinationlocation according to the at least one of the plurality of operationstyles by which the operator operates the motor vehicle to betransmitted by the mobile communication device to be stored remotely.

Example 27 may include a method, which may include: receiving data fromone or more sensors as to one or more characteristics of operation of anoperator of a motor vehicle; receiving motor vehicle locationinformation from a location system to indicate a location of the motorvehicle; obtaining an input of a destination location; and providing aroute for the operator from the motor vehicle location to thedestination location according to the at least one of the plurality ofoperation styles by which the operator operates the motor vehicle and atleast one of a plurality of route types associated with the operationstyles, wherein the at least one of the plurality of operation styles bywhich the operator operates the vehicle is determined based at least inpart on the data received from the one or more sensors.

Example 28 may include the method of example 27, wherein the method mayfurther comprise determining the at least one of the plurality ofoperation styles based at least in part on the data received from theone or more sensors.

Example 29 may include the method of example 27 or 28, wherein themethod may further comprise determining the at least one of theplurality of operation styles without an explicit input by the operatorof the at least one of the plurality of route types.

Example 30 may include the method of example 27 or 28, wherein theplurality of route types may include one or more of a fuel-efficientroute and a safe route.

Example 31 may include the method of example 27 or 28, wherein themethod may further include communicating with a mobile communicationdevice.

Example 32 may include the method of example 31 wherein the methodfurther may comprise providing the at least one of the plurality ofoperation styles by which an operator operates the motor vehicle to themobile communication device to be transmitted by the mobilecommunication device to be stored remotely.

Example 33 may include the method of example 31 wherein the method mayfurther comprise providing to the mobile communication device the routefrom the motor vehicle location to the destination location according tothe at least one of the plurality of operation styles by which theoperator operates the motor vehicle to be transmitted by the mobilecommunication device to be stored remotely.

Example 34 may include a system, which may comprise: means to receivedata from one or more sensors as to one or more characteristics ofoperation of an operator of a motor vehicle; means to receive motorvehicle location information from a location system to indicate alocation of the motor vehicle; means to obtain a destination location;and means to provide a route for the operator from the motor vehiclelocation to the destination location according to the at least one ofthe plurality of operation styles by which the operator operates themotor vehicle or at least one of a plurality of route types associatedwith the operation styles, wherein the at least one of the plurality ofoperation styles by which the operator operates the vehicle isdetermined based at least in part on the data received from the one ormore sensors.

Example 35 may include the system of example 34, wherein the system mayfurther comprise means to determine the at least one of the plurality ofoperation styles based at least in part on the data received from theone or more sensors.

Example 36 may include the system of example 34 or 35, wherein thesystem may further comprise means to determine the at least one of theplurality of operation styles without an explicit input by the operatorof the at least one of the plurality of route types.

Example 37 may include the system of example 34 or 35, wherein theplurality of route types includes one or more of a fuel-efficient routeand a safe route.

Example 38 may include the system of example 34 or 35, wherein thesystem may further comprise means to communicate with a mobilecommunication device.

Example 39 may include the system of example 38 wherein the system mayfurther comprise means to provide the at least one of the plurality ofoperation styles by which an operator operates the motor vehicle to themobile communication device to be transmitted by the mobilecommunication device to be stored remotely.

Example 40 may include the system of example 38 wherein the system mayfurther comprise means to provide to the mobile communication device theroute from the motor vehicle location to the destination locationaccording to the at least one of the plurality of operation styles bywhich the operator operates the motor vehicle to be transmitted by themobile communication device to be stored remotely.

Although certain embodiments have been illustrated and described hereinfor purposes of description, a wide variety of alternate and/orequivalent embodiments or implementations calculated to achieve the samepurposes may be substituted for the embodiments shown and describedwithout departing from the scope of the present disclosure. Thisapplication is intended to cover any adaptations or variations of theembodiments discussed herein, limited only by the claims.

What is claimed:
 1. At least one non-transitory machine-readable mediumcomprising instructions, which when executed by hardware of a vehiclenavigation system for a vehicle, cause the hardware to performoperations to: obtain a destination location for the vehicle; determinea plurality of routes to the destination location, the plurality ofroutes including route attributes obtained from map data; determine adriving style used to operate the vehicle; calculate energy use of thevehicle from the driving style and the route attributes; and output aroute from the plurality of routes based on the calculated energy useand opportunity for stops on the route.
 2. The at least onemachine-readable medium of claim 1, wherein the route attributesobtained from map data include a road type.
 3. The at least onemachine-readable medium of claim 2, wherein the road type includes afreeway, a backroad, or a toll road.
 4. The at least onemachine-readable medium of claim 1, the instructions further to providethe route to an operator of the vehicle.
 5. The at least onemachine-readable medium of claim 4, wherein the operations to providethe route to the operator of the vehicle include operations to send theroute to a display of the vehicle navigation system.
 6. The at least onemachine-readable medium of claim 4, wherein the operations to providethe route to the operator of the vehicle includes operations to providethe route to a mobile wireless device of the operator.
 7. The at leastone machine-readable medium of claim 4, the instructions further toindicate, to the operator, a stop on the route.
 8. A vehicle navigationsystem for a vehicle, the vehicle navigation system comprising: a memorycomprising instructions; and processing circuitry that, when inoperation, is configured by the instructions to: obtain a destinationlocation for a vehicle that includes the vehicle navigation system;determine a plurality of routes to the destination location, theplurality of routes including route attributes obtained from map data;determine a driving style used to operate the vehicle; calculate energyuse of the vehicle from the driving style and the route attributes; andoutput a route from the plurality of routes based on the calculatedenergy use and opportunity for stops on the route.
 9. The vehiclenavigation system of claim 8, wherein the route attributes from map datainclude a road type.
 10. The vehicle navigation system of claim 9,wherein the road type includes a freeway, a backroad, or a toll road.11. The vehicle navigation system of claim 8, wherein the instructionsconfigure the processing circuitry to provide the route to an operatorof the vehicle.
 12. The vehicle navigation system of claim 11, wherein,to provide the route to the operator of the vehicle, the processingcircuitry is configured to send the route to a display of the vehiclenavigation system.
 13. The vehicle navigation system of claim 11,wherein, to provide the route to the operator of the vehicle, theprocessing circuitry is configured to provide the route to a mobilewireless device of the operator.
 14. The vehicle navigation system ofclaim 11, wherein the instructions configure the processing circuitry toindicate, to the operator of the vehicle, a stop on the route.
 15. Avehicle comprising: a touch screen display; and a vehicle navigationsystem comprising hardware configured to: obtain a destination locationfor the vehicle from input entered into the touch screen display;determine a plurality of routes to the destination location, theplurality of routes including route attributes obtained from map data;determine a driving style used to operate the vehicle; calculate energyuse of the vehicle from the driving style and the route attributes; andoutput a route from the plurality of routes based on the calculatedenergy use and opportunity for stops on the route.
 16. The vehicle ofclaim 15, wherein the route attributes obtained from map data include aroad type.
 17. The vehicle of claim 16, wherein the road type includes afreeway, a backroad, or a toll road.
 18. The vehicle of claim 15,wherein the vehicle navigation system is configured to provide the routeto an operator of the vehicle.
 19. The vehicle of claim 18, wherein theroute is provided to the operator of the vehicle on the touch screendisplay.
 20. The vehicle of claim 18, wherein the route is provided tothe operator of the vehicle by a mobile wireless device of the operator.21. The vehicle of claim 18, wherein the vehicle navigation system isconfigured to indicate, to the operator, a stop on the route.